Preserve new snippet drafts when creation fails - #669

Summary

• save each submitted new snippet as a per-user local draft before the GitHub request
• keep saved drafts separate from the fresh New Snippet editor instead of silently restoring them
• show the draft creation timestamp with explicit Load draft and Drop draft actions
• warn in the editor footer that submitting without loading the draft will discard it
• keep the editor open on request failure and clear the draft only after successful creation
• explain recovery in localized notifications and UI copy

User experience

When a saved draft exists, users continue to see the normal fresh editor. They can load the local draft explicitly or drop it. Loading restores its description, privacy setting, filenames, and contents. Submitting different content replaces the old local draft; a successful GitHub creation clears it.

Draft available

Draft loaded

Testing

• npm run lint
• npm run test:unit (216 tests)
• npm run test:smoke (Electron app launch plus authenticated render fixtures)
• dedicated new-draft fixture verifies fresh content, timestamped callout, footer warning, Load, and Drop behavior

Live GitHub Gist creation was not exercised against a real account; failure and recovery behavior is covered by focused unit tests and the Electron fixture flow.

Closes #414